Changed E2 spawn behavior to only run once ever #3215
Conversation
|
Bit controversial, but I see more good then bad in that |
|
Might break a lot of chips |
|
I think the policy for compatibility breaks calls for community involvement |
|
I'm not sure how many E2s out in the wild rely on doing something different between |
It seems to be |
|
That said... behavior differences depending on 'strict' also sounds really strange. It makes sense for 'strict' to invoke errors or warnings, but to function differently when duping is kind of uncanny. |
|
Well, behavioral differences is kinda already a thing with persist/global scope vars. Tho it would make more sense to have API versioning instead of strict mode, so we can forget about backwards compatibilities on major releases |
|
Out of 112 polled, the majority (86) voted to accept this behavior. |
If
AdvDupe2is undefined,duped()will always run,else,
duped()will only run if the chip is not strict.This also changes
duped()anddupefinished()to be synonymous when AdvDupe2 is installed. Both will be1when thedupefinished()case is ran. Although it's not equivalent (becauseduped()is ran before constraints are created), you can now useduped()to flag both post-AdvDupe2 and regular post-dupe.I'm not sure if this is the best solution, but AdvDupe2 is the only addon that provides a hook to run after all of pasting is finished for both the normal and alternate duplicator.